Configurable data windows for archived relations

ABSTRACT

Techniques for managing configurable data windows for streams and/or archived relations are provided. In some examples, a query that identifies at least a data stream or an archived relation may be identified. Additionally, a configurable window size may be identified. In some instances, the query may be initialized with at least a portion of the historical data based at least in part on the window size. Further, the query may be evaluated based at least in part on the data stream and the portion of the historical data.

CROSS REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of, and claims the benefit and priority to application Ser. No. 13/830,129, filed Mar. 14, 2013, entitled “CONFIGURABLE DATA WINDOWS FOR ARCHIVED RELATIONS,” which claims the benefit and priority under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 61/707,641, filed Sep. 28, 2012, entitled “REAL-TIME BUSINESS EVENT ANALYSIS AND MONITORING,” the entire contents of each are incorporated herein by reference for all purposes. This application is also related to application Ser. No. 13/829,958, entitled “MANAGING CONTINUOUS QUERIES WITH ARCHIVED RELATIONS,” and application Ser. No. 13/830,428, entitled “PROCESSING EVENTS FOR CONTINUOUS QUERIES ON ARCHIVED RELATIONS,” the entire contents of each are hereby incorporated by reference for all purposes.

BACKGROUND

In traditional database systems, data is stored in one or more databases usually in the form of tables. The stored data is then queried and manipulated using a data management language such as a structured query language (SQL). For example, a SQL query may be defined and executed to identify relevant data from the data stored in the database. A SQL query is thus executed on a finite set of data stored in the database. Further, when a SQL query is executed, it is executed once on the finite data set and produces a finite static result. Databases are thus best equipped to run queries over finite stored data sets.

A number of modern applications and systems however generate data in the form of continuous data or event streams instead of a finite data set. Examples of such applications include but are not limited to sensor data applications, financial tickers, network performance measuring tools (e.g. network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like. Such applications have given rise to a need for a new breed of applications that can process the data streams. For example, a temperature sensor may be configured to send out temperature readings.

Managing and processing data for these types of event stream-based applications involves building data management and querying capabilities with a strong temporal focus. A different kind of querying mechanism is needed that comprises long-running queries over continuous unbounded sets of data. While some vendors now offer product suites geared towards event streams processing, these product offerings still lack the processing flexibility required for handling today's events processing needs.

BRIEF SUMMARY

Continuous queries in the presence of archived relations with configurable data windows may be provided. In some examples, a system may be provided, the system may include memory storing instructions and/or processors configured to access the memory and execute the instructions to at least identify a query that identifies at least a data stream. The system may also execute the instructions to identify a configurable window size. Additionally, in some examples, the system may execute the instructions to initialize the query with at least a portion of historical data based at least in part on the window size. Further, the system may also be configured to execute the instructions to evaluate the query based at least in part on the data stream and the portion of the historical data. In some aspects, the query may comprise a continuous query configured to process incoming real-time business event data of the data stream. The evaluation of the query may include at least applying the query against the data stream based at least in part on the configurable window size. Additionally, in some examples, the data stream may comprise a relation configured with a second configurable window size for referencing a portion of the data stream within a second window with a size based at least in part on second configurable window size.

Additionally, in some examples, the second window may be configured to move along the data stream with time. The historical data may not be included in the data stream at a time after initializing the query. And, the historical data may include business event data from the data stream at a time before initializing the query. In some examples, the system may also be configured to execute the instructions to at least evaluate the query by at least forming a query graph with nodes representing operators of the query. Additionally, at least one of the nodes may identify the window size. Further, in some aspects, the system may be configured to execute the instructions to at least traverse the query graph topographically from a source. The one or more processors may also be configured to execute the instructions to at least initialize the query with at least the historical data at a lowest stateful operator identified in the query graph.

Additionally, in some examples, a computer-readable memory may be provided. The memory may be configured to store instructions that cause one or more processors to receive a continuous query configured to process an archived relation, the continuous query including at least one of an identifier of the data stream or an identifier of historical data. The instructions may also cause the processors to generate a query graph based at least in part on the continuous query. Additionally, in some examples, the instructions may cause the processors to receive a window size from an entity associated with the archived relation. In some aspects, the instructions may also cause the processors to initialize the continuous query with at least a portion of historical data. Further, in some examples, the instructions may cause the one or more processors to evaluate the continuous query with respect to the archived relation and the window size based at least in part on the query graph. The archived relation may be based at least in part on the historical data. In some aspects, at least one of the archived relation or the historical data may be identified by a data definition language annotation of the continuous query. The data definition language annotation may identify at least one of a location of the historical data, a source of the archived relation, a data object associated with the archived relation, operation information associated with processing the continuous query, one or more relevant columns of a database corresponding to the historical data, a data object corresponding to output of the continuous query, or a location for providing the output of the continuous query. Additionally, in some examples, the plurality of instructions may further comprise instructions that cause the one or more processors to determine an amount of historical data with which to initialize the continuous query based at least in part on the window size. Further, the continuous query may be initialized with the at least a portion of the historical data at a stateful operator of the query graph while traversing the query graph topographically from a source of the query graph.

Further, in some examples, a computer-implemented method may be provided. The method may be configured to receiving a continuous query configured to process an archived relation associated with business event data, the continuous query including an identifier of the archived relation and an identifier of historical data associated with the stream. Additionally, the method may be configured to receive a window size configured to identify a bounded range of the archived relation to process. The method may also be configured to generate a query graph based at least in part on the continuous query, the query graph including at least a node representing an operator of the continuous query. Additionally, in some aspects, the method may be configured to traverse the query graph topographically from a source node of the query graph to identify a stateful operator. The method may also be configured to initialize the continuous query with at least a portion of historical data at the identified stateful operator and/or evaluate the continuous query with respect to the archived relation based at least in part on the window size. In some aspects, the historical data may include business event data from a point in time of the archived relation prior to initializing the continuous query. Additionally, in some aspects, the method may also be configured to determine an optimal amount of the historical data with which to initialize the continuous query based at least in part on the operator of the continuous query. Further, the method may also be configured to determine an optimal amount of the historical data with which to initialize the continuous query based at least in part on the window size.

The foregoing, together with other features and embodiments, will become more apparent upon referring to the following specification, claims, and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the FIG. in which the reference number first appears. The use of the same reference numbers in different FIGS. indicates similar or identical items.

FIG. 1 is a simplified block diagram illustrating an example architecture for managing continuous queries with archived relations, according to at least one example.

FIG. 2 is a simplified block diagram illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 3 is a simplified block diagram illustrating at least some additional features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 4 is a simplified block diagram illustrating at least some additional features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 5 is a simplified block diagram illustrating at least some additional features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 6 is a simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 7 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 8 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 9 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 10 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 11 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 12 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 13 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 14 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 15 is a simplified block diagram illustrating components of a system environment that may be used in accordance with an embodiment of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 16 is a simplified block diagram illustrating a computer system that may be used in accordance with embodiments of the management of continuous queries with archived relations described herein described herein, according to at least one example.

FIG. 17 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 18 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

FIG. 19 is another simplified process flow illustrating at least some features of the management of continuous queries with archived relations described herein, according to at least one example.

DETAILED DESCRIPTION

In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. However, it will also be apparent to one skilled in the art that the embodiments may be practiced without the specific details. Furthermore, well-known features may be omitted or simplified in order not to obscure the embodiment being described.

In some examples, mechanisms to support continuous query language (CQL) queries (also referred to as “query statements”) with one or more archived relations, for example, including but not limited to, a CQL relation this may be non-empty when created, may be provided. For example, in some scenarios, a CQL relation may be defined by applying a window on a stream. In other words, a relation may be a bounded dataset. For example, given an event stream, a relation may be first be defined by a window that includes a particular number or set of elements of the stream (e.g., within the window). However, a relation may, in some cases, be created in an empty state. That is, the window may be defined; however no events may be included the relation. On the other hand, an archived relation may include event data upon creation. In some examples, an archiver or other data object may be responsible for managing the real-time data to be utilized in creation of the archived relation and/or may provide this data to an engine configured to generate or otherwise manage the archived relations.

Additionally, in some examples, mechanisms for supporting the CQL queries with archived relations may also enable configuration of particular data windows of the archived relations. These data windows may be configured, generated, managed, updated, and/or otherwise manipulated by a user, administrator, or other entity associated with the archived relation and/or event data (e.g., business event data) of a user. Further, in some examples, archived relations within continuous queries may be implemented in such a way as to avoid missing and/or double counting change notifications. For example, when a query is run, it may initially be run against a data object backing store to establish the current state of the query, and then listen for and process change notification from that data object. However, change notifications may be missed while a complex event process (CEP) implementing the query is running the initial query. Additionally, change notifications may also be double-counted if the change is already in the initial query. Yet, in some examples, missed and/or double-counting change notifications may be avoided by establishing a listener before the initial query and/or utilizing a transaction identifier (TID), a context identifier (CID), or other mechanism for managing change events.

In general, a continuous data stream (also referred to as an event stream) may include a stream of data or events that may be continuous or unbounded in nature with no explicit end. Logically, an event or data stream may be a sequence of data elements (also referred to as events), each data element having an associated timestamp. A continuous event stream may be logically represented as a bag or set of elements (s, T), where “s” represents the data portion, and “T” is in the time domain. The “s” portion is generally referred to as a tuple or event. An event stream may thus be a sequence of time-stamped tuples or events.

In some aspects, the timestamps associated with events in a stream may equate to a clock time. In other examples, however, the time associated with events in an event stream may be defined by the application domain and may not correspond to clock time but may, for example, be represented by sequence numbers instead. Accordingly, the time information associated with an event in an event stream may be represented by a number, a timestamp, or any other information that represents a notion of time. For a system receiving an input event stream, the events arrive at the system in the order of increasing timestamps. There could be more than one event with the same timestamp.

In some examples, an event in an event stream may represent an occurrence of some worldly event (e.g., when a temperature sensor changed value to a new value, when the price of a stock symbol changed) and the time information associated with the event may indicate when the worldly event represented by the data stream event occurred.

For events received via an event stream, the time information associated with an event may be used to ensure that the events in the event stream arrive in the order of increasing timestamp values. This may enable events received in the event stream to be ordered based upon their associated time information. In order to enable this ordering, timestamps may be associated with events in an event stream in a non-decreasing manner such that a later-generated event has a later timestamp than an earlier-generated event. As another example, if sequence numbers are being used as time information, then the sequence number associated with a later-generated event may be greater than the sequence number associated with an earlier-generated event. In some examples, multiple events may be associated with the same timestamp or sequence number, for example, when the worldly events represented by the data stream events occur at the same time. Events belonging to the same event stream may generally be processed in the order imposed on the events by the associated time information, with earlier events being processed prior to later events.

The time information (e.g., timestamps) associated with an event in an event stream may be set by the source of the stream or alternatively may be set by the system receiving the stream. For example, in certain embodiments, a heartbeat may be maintained on a system receiving an event stream, and the time associated with an event may be based upon a time of arrival of the event at the system as measured by the heartbeat. It is possible for two events in an event stream to have the same time information. It is to be noted that while timestamp ordering requirement is specific to one event stream, events of different streams could be arbitrarily interleaved.

An event stream has an associated schema “S,” the schema comprising time information and a set of one or more named attributes. All events that belong to a particular event stream conform to the schema associated with that particular event stream. Accordingly, for an event stream (s, T), the event stream may have a schema ‘S’ as (<time stamp>, <attribute(s)>), where <attributes> represents the data portion of the schema and can comprise one or more attributes. For example, the schema for a stock ticker event stream may comprise attributes <stock symbol>, and <stock price>. Each event received via such a stream will have a time stamp and the two attributes. For example, the stock ticker event stream may receive the following events and associated timestamps:

... (<timestamp_N>, <NVDA,4>) (<timestamp_N+1>, <ORCL,62>) (<timestamp_N+2>, <PCAR,38>) (<timestamp_N+3>, <SPOT,53>) (<timestamp_N+4>, <PDCO,44>) (<timestamp_N+5>, <PTEN,50>) ... In the above stream, for stream element (<timestamp_N+1>, <ORCL,62>), the event is <ORCL,62> with attributes “stock_symbol” and “stock_value.” The timestamp associated with the stream element is “timestamp_N+1”. A continuous event stream is thus a flow of events, each event having the same series of attributes.

As noted, a stream may be the principle source of data that CQL queries may act on. A stream S may be a bag (also referred to as a “multi-set”) of elements (s, T), where “s” is in the schema of S and “T” is in the time domain. Additionally, stream elements may be tuple-timestamp pairs, which can be represented as a sequence of timestamped tuple insertions. In other words, a stream may be a sequence of timestamped tuples. In some cases, there may be more than one tuple with the same timestamp. And, the tuples of an input stream may be requested to arrive at the system in order of increasing timestamps. Alternatively, a relation (also referred to as a “time varying relation,” and not to be confused with “relational data,” which may include data from a relational database) may be a mapping from the time domain to an unbounded bag of tuples of the schema R. In some examples, a relation may be an unordered, time-varying bag of tuples (i.e., an instantaneous relation). In some cases, at each instance of time, a relation may be a bounded set. It can also be represented as a sequence of timestamped tuples that may include insertions, deletes, and/or updates to capture the changing state of the relation. Similar to streams, a relation may have a fixed schema to which each tuple of the relation may conform. Further, as used herein, a continuous query may generally be capable of processing data of (i.e., queried against) a stream and/or a relation. Additionally, the relation may reference data of the stream.

In some examples, business intelligence (BI) may help drive and optimize business operations at particular intervals (e.g., on a daily basis in some cases). This type of BI is usually called operational business intelligence, real-time business intelligence, or operational intelligence (OI). Operational Intelligence, in some examples, blurs the line between BI and business activity monitoring (BAM). For example, BI may be focused on periodic queries of historic data. As such, it may have a backward-looking focus. However, BI may also be placed into operational applications, and it may therefore expand from a mere strategic analytical tool into the front lines in business operations. As such, BI systems may also be configured to analyze event streams and compute aggregates in real time.

In some examples, a continuous query language service (CQ Service) may be configured to extend a BI analytics server to handle continuous queries and enable real-time alerts. The CQ Service, in some aspects, may provide integration with a BI analytics server and a CQL engine. By way of example only, a BI analytics server may delegate continuous queries to the CQ Service and the CQ Service may also act as a logical database (DB) gateway for a CQL engine. In this way, the CQL engine may be able to leverage the BI analytics server for its analytics capabilities and semantic modeling.

In some examples, the CQ Service may provide, among other things, the following functionalities:

-   -   Remoting service for BI Analytics Server as CQL engine Gateway;     -   Event source/sink adapter;     -   Generate data definition languages (DDLs) from logical SQL plus         CQL extensions;     -   Provide unified model for all types of continuous queries and         implementation selections;     -   Maintain metadata and support restartability; and     -   High availability and scalability support.

Additionally, in some examples, OI is a form of real-time dynamic, business analytics that can deliver visibility and insight into business operations. OI is often linked to or compared with BI or real-time BI, in the sense that both help make sense out of large amounts of information. But there are some basic differences: OI may be primarily activity-centric, whereas BI may be primarily data-centric. Additionally, OI may be more appropriate for detecting and responding to a developing situation (e.g., trend and pattern), unlike BI which may traditionally be used as an after-the-fact and report-based approach to identifying patterns.

In some examples, a business event analysis and monitoring (BEAM) system may include a CQL engine to process and/or receive in-flight data. For example, a CQL engine may be an in-memory real-time event processing engine configured to query or otherwise process incoming real-time information (e.g., BI or OI). The CQL engine may utilize or understand temporal semantics and be configured to allow definition of a window of data to process. Utilizing a CQL engine may, in some cases, involve always running a query on incoming data.

In some aspects, the CQL engine may include a full blown query language. As such, a user may specify computations in terms of a query. Additionally, the CQL engine may be designed for optimizing memory, utilizing query language features, operator sharing, rich pattern matching, rich language constructs, etc. Additionally, in some examples, the CQL engine may process both historical data and streaming data. For example, a user can set a query to send an alert when California sales hit above a certain target. Thus, in some examples, the alert may be based at least in part on historical sales data as well as incoming live (i.e., real-time) sales data.

In some examples, the CQL engine or other features of the below described concepts may be configured to combine a historical context (i.e., warehouse data) with incoming data in a real-time fashion. Thus, in some cases, the present disclosure may describe the boundary of database stored information and in-flight information. Both the database stored information and the inflight information may include BI data. As such, the database may, in some examples, be a BI server or it may be any type of database. Further, in some examples, the features of the present disclosure may enable the implementation of the above features without users knowing how to program or otherwise write code. In other words, the features may be provided in a feature-rich user interface (UI) or other manner that allows non-developers to implement the combination of historical data with real-time data.

In some examples, the above concepts may be utilized to leverage the rich real-time and continuous event processing capabilities associated with complex event processing. Several features may be supported such as, but not limited to, archived relations. As such, in order to leverage such features (e.g., rich, real-time and continuous event processing), the system may be configured to transparently deal with startup state and runtime state of relational data. In other words, the system may be configured to manage a query that is non-empty at the instant of its creation (i.e., an archived relation).

In some examples, an archived relation may be utilized. As such, when a CQL engine sees a query that indicates that it is based on an archived relation; that archived relation may also indicate that there are certain entities it can call to query for historical context, for example. In some examples, a data definition language (DDL) may indicate annotations about the archived relation such as, but not limited to, how do to the query, what are the important columns in the table, and/or where to send the rest of the data. In some examples, once the query is constructed in the CQL engine (e.g., as a graph), the system may analyze the query graph. Additionally, in some aspects, there are certain operators that are stateful, like “distinct,” “group aggr,” “pattern,” and/or “group by.” However, stateless operators may just take input and send it to the parent, for example, down-stream operators. So, one approach is to store this entire table here. However, utilizing archived relations, the system may analyze the query graph and decide which of the lowest stateful operator that it can use to query the archive. In some examples, the system (or one or more computer-implemented methods) may retrieve the state at the lowest stateful operator reached while traversing the graph. For example, the query graph may be analyzed in a topological order from the source. Based at least in part on this first stateful operator, the CQL engine may then determine the optimal amount of data to be fetched in order to initialize the state of the operators for a query defined over an archived relation.

In at least one non-limiting example, source operators like relation and/or source may come first in the topological traversal with query output and/or root coming last. For example, if the CQL query looks like: select sum(c1) from R1 where c2>c25, the plan for this query may look like: RelationSource→SELECT→GroupAggr. Thus, following the topological order, and since RelationSource and SELECT are both stateless, the lowest stateful operator may be GroupAggr. In this way, the stateful operators of a query (GroupAggr in this example) may enable the query engine to populate the query engine with historical data from a data store prior to receiving streaming data. This may be enabled based at least in part on the fact that the query is analyzing an archived relation and the archived relation has been indicated as such.

In some examples, a window size for a given archive relation may be specified by a user. A window, in some aspects, in relation to an archived relation, may include a node in a query graph that analyzes or otherwise evaluates incoming streamed content. In other words, the window may define the amount of streamed content that me analyzed and/or processed by the query engine and/or the amount of historical data that will be included in the archived relation.

At a high level, once a window is applied on a Stream it becomes a Relation and then regular relational logic may be applied, as with relational databases. As tuples arrive and leave the window, the Relation under consideration changes with queries compiled against it emitting results at the same time. CQL may support RANGE (up to nanoseconds granularity), ROWS, PARTITION BY and extensible windows. These windows are examples of stream-to-relation operators. On the other hand, ISTREAM (i.e., insert stream), DSTREAM (i.e., delete stream) and RSTREAM (i.e., relation stream) are relation-to-stream operators. In some examples, a user, developer, and/or manager may set the window size (e.g., via a UI) provided by the query engine or one or more computing systems operating or hosting the query engine. In some examples, a window on a stream may be a time-based range window. For example, a configurable value window on an archived relation may be specified using window size and the attribute on which the window is calculated. When there is a configurable value window specified on top of archived relation, a snapshot query may be computed and the snapshot tuples which are within window limits may be output. Additionally, after state initialization, the value window may be applied on incoming active data. In some examples, only the incoming active data will be inserted into window whose window attribute's value is differing from current event time for less than the window size.

Additionally, in some examples, features of the present disclosure may also leverage the continuous query processing capabilities of the CQL engine and/or CEP engine to support real-time data analysis. In some aspects, the CQL engine and/or CEP engine may have traditionally been a stream-oriented analysis engine; however, it may be enhanced to support stream-oriented data that is backed by a durable store (e.g., the archived relation described above). For example, the present disclosure describes features that may support the notion of a data object (DO) which is a durable store (database and/or table). Modifications made to a DO may cause change notifications to be broadcast to interested listeners creating, in effect, a data stream. This data stream may be consumed by the CQL engine and/or CEP engine in support of any running queries; however, the CQL engine and/or CEP engine may not have been designed to take into account the existing data in the DO backing store. For example, the CQL engine and/or CEP engine may request that the initial state of the query running in the CQL engine and/or CEP engine reflect the current state of the DO including all the data currently in the DO backing store. Once this query is so initialized, the CQL engine and/or CEP engine only need to concern itself with the stream of DO change notifications from that point on in traditional stream-oriented style.

In some aspect, the CQL engine and/or CEP engine may traditionally process streams or non-archived relations, so there may be no initial state. For example, a query may be loaded, wherein it may start running and listening for changes, etc. In some cases, if a user asks for sales by state, in a bar chart, and then somebody makes a new sale, the table may get updated and the user may expect to see a change in the graph, pushed out to them. However, if they close the dashboard and come back a week later and bring up some sales, the user may expect to have the sum of sales according to the table of summed sales data. In other words, the query may need to bring the query up to the state of the archive and then listen for active changes.

In some aspects, for example, the CQL engine may be pre-initialized with the archived data. Once initialized, the CQL engine may listen to a Java Messaging Service (JMS) or other messenger for change notifications (e.g., based at least in part on API calls for inserting, deleting, etc., data from the archive). Thus, services can listen and if the JMS publishes on the same topic that the listening service is listening on, it may receive the data. The services don't have to know who is publishing or whether they are, or not. The listening service can just listen, and if something happens, the listening service may hear it. In some examples, this is how persistence is decoupled, for instance, from its consumers. Additionally, in some examples, an alert engine may raise alerts based on what the alert engine hears, potentially, and further, a SQL engine, that may be listening in on process queries of relevance to the listener.

In some examples, a query may be started in CQL, SQL, and/or CEP engine and instructions may be configured to get the archive data (e.g., to prime the pump) and then start listening to these JMS messages. However, with numerous inserts, deletes, etc., this could include a large amount of information. Additionally, there could be a lag time before the message is heard by the listener and the listening may, in some examples, jump in, query the archive, come back, and start listening. Thus, there is a potential for missing and/or double counting an event.

Additionally, if the engine merely runs the query, while it's running the query things can go into JMS and be published where the engine wasn't listening. So, the engine may be configured to setup the listener first, run the archive query, and then come back and actually start pulling out of the queue, so that it doesn't miss anything. Thus, the JMS may queue things up and, if things back up it's okay while the engine is doing a query because it can catch up later and it doesn't have to worry about whether it's synchronous. If it's not here, listening, it won't miss it, it just gets queued until the engine comes back, as long as it has its listener established.

Additionally, in some examples, a system column may be added to a user's data. This system column may be for indicating transaction IDs to attempt to handle the double counting and/or missing operation problem. However, in other examples, the system may provide or otherwise generate a transaction context table. Additionally, there may be two additional columns TRANSACTION_CID and TRANSACTION_TID. The context table may always be maintained by persistence service so as to know thread (context)wise of the last committed transaction ID. The transaction IDs may be guaranteed to be committed in ascending order for a thread (context). For example, when a server comes up, it may run the persistence service. Each one may allocate a set of context IDs and transaction IDs for determining whether data of the pre-initialized information includes all of the data that has passed through the JMS. Additionally, in some cases, multiple output servers may be utilized (in compliance with JTA and/or to implement high availability (HA), wherein each server may manage a single set of context/transaction tables that are completely separate from the other tables managed by the other servers.

The techniques described above and below may be implemented in a number of ways and in a number of contexts. Several example implementations and contexts are provided with reference to the following figures, as described below in more detail. However, the following implementations and contexts are but a few of many.

FIG. 1 depicts a simplified example system or architecture 100 in which techniques for managing continuous queries with archived relations may be implemented. In architecture 100, one or more users 102 (e.g., account holders) may utilize user computing devices 104(1)-(N) (collectively, “user devices 104”) to access one or more service provider computers 106 via one or more networks 108. In some aspects, the service provider computers 106 may also be in communication with one or more streaming data source computers 110 and/or one or more databases 112 via the networks 108. For example, the users 102 may utilize the service provider computers 106 to access or otherwise manage data of the streaming data source computers 110 and/or the databases 112 (e.g., queries may be run against either or both of 110, 112). The databases 112 may be relational databases, SQL servers, or the like and may, in some examples, manage historical data, event data, relations, archived relations, or the like on behalf of the users 102. Additionally, the databases 112 may receive or otherwise store data provided by the streaming data source computers 110. In some examples, the users 102 may utilize the user devices 104 to interact with the service provider computers 106 by providing queries (also referred to as “query statements”) or other requests for data (e.g., historical event data, streaming event data, etc.). Such queries or requests may then be executed by the service provider computers 106 to process data of the databases 112 and/or incoming data from the streaming data source computers 110. Further, in some examples, the streaming data source computers 110 and/or the databases 112 may be part of an integrated, distributed environment associated with the service provider computers 106.

In some examples, the networks 108 may include any one or a combination of multiple different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, intranet systems, and/or other private and/or public networks. While the illustrated example represents the users 102 accessing the service provider computers 106 over the networks 108, the described techniques may equally apply in instances where the users 102 interact with one or more service provider computers 106 via the one or more user devices 104 over a landline phone, via a kiosk, or in any other manner. It is also noted that the described techniques may apply in other client/server arrangements (e.g., set-top boxes, etc.), as well as in non-client/server arrangements (e.g., locally stored applications, etc.).

The user devices 104 may be any type of computing device such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a laptop computer, a desktop computer, a thin-client device, a tablet PC, etc. In some examples, the user devices 104 may be in communication with the service provider computers 106 via the networks 108, or via other network connections. Further, the user devices 104 may also be configured to provide one or more queries or query statements for requesting data of the databases 112 (or other data stores) to be processed.

In some aspects, the service provider computers 106 may also be any type of computing devices such as, but not limited to, mobile, desktop, thin-client, and/or cloud computing devices, such as servers. In some examples, the service provider computers 106 may be in communication with the user devices 104 via the networks 108, or via other network connections. The service provider computers 106 may include one or more servers, perhaps arranged in a cluster, as a server farm, or as individual servers not associated with one another. These servers may be configured to perform or otherwise host features described herein including, but not limited to, the management of archived relations, configurable data windows associated with archived relations, and/or accurately counting change events associated with managing archived relations described herein. Additionally, in some aspects, the service provider computers 106 may be configured as part of an integrated, distributed computing environment that includes the streaming data source computers 110 and/or the databases 112.

In one illustrative configuration, the service provider computers 106 may include at least one memory 136 and one or more processing units (or processor(s)) 138. The processor(s) 138 may be implemented as appropriate in hardware, computer-executable instructions, firmware, or combinations thereof. Computer-executable instruction or firmware implementations of the processor(s) 138 may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described.

The memory 136 may store program instructions that are loadable and executable on the processor(s) 138, as well as data generated during the execution of these programs. Depending on the configuration and type of service provider computers 106, the memory 136 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.). The service provider computers 106 or servers may also include additional storage 140, which may include removable storage and/or non-removable storage. The additional storage 140 may include, but is not limited to, magnetic storage, optical disks, and/or tape storage. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices. In some implementations, the memory 136 may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM.

The memory 136, the additional storage 140, both removable and non-removable, are all examples of computer-readable storage media. For example, computer-readable storage media may include volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. The memory 136 and the additional storage 140 are all examples of computer storage media.

The service provider computers 106 may also contain communications connection(s) 142 that allow the identity interface computers 120 to communicate with a stored database, another computing device or server, user terminals, and/or other devices on the networks 108. The service provider computers 106 may also include input/output (I/O) device(s) 144, such as a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, one or more speakers, a printer, etc.

Turning to the contents of the memory 136 in more detail, the memory 136 may include an operating system 146 and one or more application programs or services for implementing the features disclosed herein including at least an archived relation module 148, a configurable window module 150, and/or an event counting module 152. As used herein, modules may refer to programming modules executed by servers or clusters of servers that are part of a service. In this particular context, the modules may be executed by the servers or clusters of servers that are part of the service provider computers 106. In some examples, the archived relation module 148 may be configured to, receive, identify, generate, or otherwise provide one or more archived relations 154 that may include reference to one or more event stream entries s1, s2, . . . , sN. For example, an archived relation may be defined by applying a window on at the stream including these entries (i.e., s1 through sN). As such, the archived relation may be the bounded dataset including these entries. However, the entries may be non-empty upon generation including, but not limited to, having one or more of the entries (e.g., s1 and/or s2, more entries, or less) of the relation pre-loaded from Persistence or some other database of historical data. As such, these pre-loaded entries may include the historical data, and the remainder of the relation may include incoming streaming data. In some examples, the archived relation 154 may first be identified as {s3, s4}. However, when the window moves from w1 to w2, the archived relation 154 may be identified as {s4, s5} and may have been changed by a delete of s3 and/or an insert of s5.

As noted above, an archived relation 154 may be a CQL relation that is (possibly) non-empty at the “instant” of its creation. This is in contrast with a “normal” CQL relations which have empty contents at the “instant” when they are created. In some examples, it is imagined as if the contents of the archived relation 154 as of the instant of its creation existed from the “beginning of time” (Long.MIN_VALUE). In the BEAM context, it is useful to note that the objects (in some examples, all the objects) of a CQL engine 156 may be created every time on server startup. In some respects, an archived relation 154 may be similar to a “normal” CQL internal relation. In particular, operations (Relation-to-Relation operations like JOIN, GROUP AGGR, ORDER BY TOP N as well as Relation-to-Stream operations like I/D/RSTREAM) may retain the same semantics as they have over “normal” CQL internal relations. Additionally, in some examples, an “archiver” may be a Java class that implements a specific contract with the CQL engine 156. It may implement the IArchiver interface or some other interface capable of enabling an archiver. This “archiver” along with the identity of the logical entity managed by the “archiver” that corresponds to the archived relation 154 (for example, the name of the Data Object) may be specified as part of the DDL statement used to create the archived relation 154.

In some aspects, the archiver may be implemented based at least in part on a contract with the CQL engine 156 to at least provide the contents of an archived relation 154 at the time of its creation. Additionally, the archiver may be expected to maintain the “time-varying” contents of the archived relation 154 on its own (e.g., external to the CQL engine 156). However, in some examples, the archiver may be stateless. In this example, the archiver may implement a method (e.g., “execute( )”) that executes the query handed to it by the archived relation framework. The archiver may then give the contents back to the archived relation framework once the method is executed. The archiver may also be configured to provide querying capabilities on the archived relation 154 (e.g., expressed as an SQL-99 query). Additionally, in some examples, FROM clause item(s) in the query presented to the “archiver” may be the name of the “archiver” entity and/or the name of the DataObject (e.g., maintained on the durable store). When the FROM clause items are the DataObject names, they may be mapped to the archived relation in the creation DDL. Additionally, or alternatively, the archiver name may be used to lookup the archiver instance (there could be more than one archiver) and then call execute(query) on that archiver instance. The attribute names used in the query may be the column names specified in a CREATE ARCHIVED RELATION DDL or other appropriate DDL, as desired. While executing a query, the “archiver” may run the query on a snapshot of the Data Object(s) that contains committed changes as of txn T_n where T_n is not earlier than the latest transaction for which events for the Data Object have been presented as streaming input. In particular, there may have been no streaming Data Object events that have been provided as input corresponding to “later” transactions.

Further, the “archiver” may return the ID of the transaction as of which this query was executed. This ID may be a monotonically increasing number (not necessarily contiguous) such that later transactions have larger IDs as compared to earlier transactions. For UPDATE events, the “archiver” may provide as part of the streaming event, the OLD as well as the NEW values. Additionally, or alternatively, in some examples, a persistence service may send the change notifications with both OLD and NEW values to the CQ Service. In this way, the CQ Service may be able to perform the appropriate operations on the archived relations. For DELETE events, the “archiver” may provide the DELETE event as a streaming event if (in some examples, “if and only if”) it passes validation (i.e., it matches with an existing Data Object record). In some examples, the functionality of the archiver may enable a scenario where there are no Data Object events that the query does not process. The CQL engine 156 may also enable a scenario where no duplicate events are processed by skipping the processing of all Data Object events with transaction identifiers<=the transaction identifier returned by the “archiver” as part of executing a “Snapshot” query. In some examples, the archiver may be comparable to a Persistence Service. Alternatively, or in addition, snapshot information at the querying instant may also be derived from the transaction context table. This snapshot information may be maintained in the CQL Engine and a snapshotID (increasing identifier) may be associated with it. The same may be set in the input queues of some selected operators in that query's plan. These are called ‘connector’ operators and they may represent the place at which a local query plan may join the global (overall) query plan. When an event arrives in CQL Engine, a snapshotID may be computed for that event using the context ID and transaction ID values in it. The snapshotID may be computed using the snapshot information maintained in CQL Engine. The snapshotID of the event may then be compared with the snapshotID of the input queue. If the ID in the event>ID in the queue then it may be processed otherwise it may have already been accounted for before and may therefore ignored to avoid double-counting.

The introduction of the archived relation 154 as a native CQL concept enables the CQL engine 156 to determine the optimal amount of data to be fetched in order to initialize the state of the operators for a query defined over the archived relation 154. In some examples, as the final step of query compilation, following the query plan generation (and/or merging with the global plan) a state initialization phase may be introduced to determine an optimal set of queries to be run against the “archiver” (e.g., for the purposes of operator state initialization). In some cases, the state initialization algorithm that is used to determine a set of queries (e.g., an optimal set) may defer materialization of state up the operator chain until a stateful operator is encountered (which aggregates data and hence may retrieve less data as compared to materialization of all details/facts in memory). The first step in query execution, even before the state initialization queries are run, may be the execution of a snapshot query and/or the delivery of the results to the client. In some examples, the snapshot query (also referred to as the “archiver query”) may be part of the state initialization where the operators may be initialized with the contents of the results. These results may then be propagated to downstream operators (e.g., all downstream operators), thus outputting the result. The queries determined by the state initialization algorithm may then be run next. At the end of this first step, all the operators may have their state appropriately initialized and the query may be ready to process the streaming events.

When a CQL query refers an archived relation 154, during system restart, the CQL engine 156 may be configure to enable a scenario where the states of execution operators in the query are initialized to the values that they had prior to a shutdown. Alternatively, or in addition, each time a query is (re)started, whether as part of shutdown or voluntarily, the query may issue a fresh or new archiver query to initialize state again. In some examples, this may be different at time t0+delta than it was at t0. In some cases, a state initialization algorithm may be configured to handle this functionality. In some examples, each (or every) archived relation 154 may map to an archiver object that keeps track of the events forming the relation and may be able to answer the SQL queries (similar to a database table) issued to it. Additionally, initializing the state of an execution operator in a CQL query may a two-step process, including at least: issuing an appropriate SQL query to the archiver that maps to the archived relation 154 on which the CQL query depends; and use the returned results to initialize the state of the operator. Deferring materialization of the events (obtained from the archiver) may result in lesser memory and/or processing time consumption. Additionally, or in the alternative, memory savings may be due to finding the appropriate operators that minimize the memory. For example, aggregated/summarized data may be brought into memory, resulting in significant memory savings.

In some examples, the state initialization process (which may be one step in the overall process, and may be implemented when a CQL query is started and is referring an archived relation(s)) may include: obtaining a logical plan for the query using the metadata object, constructing a physical plan form the logical plan, optimizing the local physical plan using an optimizer, sharing operating to get a global physical plan, adding auxiliary structures (e.g., synopsis, store, queue, etc.), and instantiating the query (e.g., constructing execution operators and/or supporting execution structures). Additionally, the appropriate location from where to call the state initialization algorithm may be right after the local physical plan optimization. In some examples, the state initialization algorithm may only be called when the query depends on or more archived relations 154.

In some examples, given binary operators, children operators may be marked as query operators. Also if after traversing the entire query plan, no query operator is identified, the root may be marked as the query operator. Once the operators are identified as query operators, during the instantiation phase if the isQueryOperator flag is set then a method to execute the constructed archiver query would be called from the Operator Factory code. The returned result set may then be converted into a set of tuples and the list may be set in the execution operator instance. In this way, upon instantiation execution operators that need a state may have a list of tuples that may be sufficient for initializing its state. Upon instantiation, one more pass may be made over the query plan in topological order in which a method that would use these tuples to initialize state and propagate it downstream may be called. This method may be operator-specific and/or the initialization processing may be similar to populating synopsis, maintaining internal data-structures, and so on.

In some examples, the following CQL query on top of a “sales” archived relation 154 may be implemented:

SELECT SUM(sales), productid FROM sales WHERE region = “APAC” GROUP BY productid

In some examples, the query plan when compiled in the CQL engine 156 may be described as: OUTPUT→PROJECT→GROUP BY AGGREGATION (<grouping key>, sum(sales))→FILTER (region=“APAC”)→REL_SOURCE (archived relation: sales).

In some examples, when the CQL engine 156 compiles the aforementioned query, it may determine that the query is expressed against a relation (e.g., the archived relation 154) whose state at startup is available externally and could potentially be large. There may be a set of operators in CQL that are stateful (e.g., GROUP BY, PATTERN) while others (e.g., FILTER, PROJECT, OUTPUT) may not be stateful. The state initialization algorithm may work as follows for the scenario in consideration: a REL_SOURCE operator may skip calling the archiver since it is stateless for archived relations. Next up is FILTER, which may also be stateless so it may skip calling the archiver for state too. Next, the GROUP BY operator may encountered, and it may invoke the archiver to fill up its state using the following SQL query (as desired, the archiver query may be a SQL query formed by using a sub-query based approach and may be more complicated than the following):

SELECT SUM(sales), COUNT(*), productid FROM SALES_DO WHERE region=”APAC” GROUP BY productid

Note that even though the user's query may not include the COUNT aggregate, the GROUP BY may issue a SQL query that has a COUNT aggregate. This may be because this piece of information may be requested by the GROUP BY operator (as part of its state) to determine whether a group (corresponding to a “productid” in this example) becomes empty so that it can release any resources (like memory) that it might be using related to the group.

Now, considering the situation where a −ve tuple arrives. In the above scenario REL_SOURCE may not maintain any state so it may let the next operator in the chain decide (rather than throw an exception as it might for a “regular” CQL relation). The FILTER operator also may not maintain any state, and it may do the same. Next, the GROUP BY operator may see the tuple. Since its state has been initialized it may be able to successfully locate the corresponding group and proceed with the rest of the processing. For example, if it is a tuple with region=“APAC” and productid=“Mobile Phones,” the SUM aggregation function may reduce the running total for “Mobile Phones” by the amount present in the tuple.

In some examples, the following CQL query on top of a “sales” archived relation 154 may be implemented for determining the median as opposed to sum, in the above example:

SELECT MEDIAN(sales), productid FROM sales WHERE region = “APAC” GROUP BY productid

In some examples, the query plan when compiled in the CQL engine 156 may described as: OUTPUT→PROJECT→GROUP BY (MEDIAN) (<grouping key>, median(sales))→FILTER (region=“APAC”)→REL_SOURCE (archived relation: sales).

In some examples, the state initialization algorithm works as follows for the scenario in consideration. The REL_SOURCE operator may skip calling the archiver since it may be stateless for archived relations. Next up is FILTER, which may also be stateless so it may skip calling the archiver for state too. Next, the GROUP BY operator may be encountered. This operator may be stateful and thus may request state initialization. Here the query involves at least one holistic function (MEDIAN), so it is may not be sufficient to bring aggregated/summary state from the database. The entire set of values over which the MEDIAN is to be calculated may be requested for the GROUP BY state.

Thus, at this stage, having identified the lowest stateful operator and determined that more detail may be requested to make up its state, the operator plan may be traversed in the opposite direction (i.e., “down”). That is, the plan may be traversed from the top down from this stage on. In some examples, the responsibility to construct the state will fall on the next operator down the tree, which in this case may be FILTER and it may issue the following SQL query (to the “archiver”) that may bring the requested set of values into memory:

SELECT sales, productid FROM SALES_DO WHERE region = “APAC”

In some examples, once these tuples are retrieved, the FILTER may propagate these values upstream and the GROUP BY may build its state by constructing a tree or graph (e.g., but not limited to, an Augmented Red-Black tree or the like). This data structure may enable very fast subsequent (O (log n) time) incremental MEDIAN calculation. In some examples, if the FILTER were absent in the above query, the responsibility to construct state may have fallen on the REL_SOURCE operator and the entire contents of the relation (as an optimization, only the relevant fields accessed by the query would be retrieved for each row as opposed to the entire row. Of course, if all fields are accessed, the entire row would be fetched) may have been brought into memory.

In some aspects, for handling minus events reaching a query based on an archived relation 154, additional support may be useful. Some of the CQL Engine 156 operators like Project, Binary operator like join maintain a lineage synopsis. The lookup in this lineage synopsis is based on a TupleId. When a PLUS tuple comes it may be inserted into the synopsis. When a MINUS tuple comes to that operator we look up the lineage synopsis which happens on the tupleId. The problem that can come in the context of an archived relation 154 is as follows:

-   -   1. When the query starts, an operator which maintains a lineage         synopsis may be identified as the query operator and it may         query the archiver and convert the returned results into tuples         and puts them in a lineage synopsis.     -   2. Additionally, when the query starts to run, the first tuple         it receives may be a MINUS corresponding to one of the archived         plus tuple. Here, the ID of the PLUS and MINUS tuple may not         match and this will lead to a failed lookup and incorrect         results.     -   3. In the normal relation case, a relation source may help         ensure that PLUS and MINUS tuples have the same IDs since it may         maintain a synopsis, but for the archived case it may not be         possible.

As such, a BEAM Persistence layer may assign an event ID to each event and INSERT (PLUS), DELETE (MINUS), and UPDATE notifications of an event may all have the same value of this ID. This facility may be utilized to avoid the problem mentioned above. Thus, one more clause may be added to the archived relation 154 DDL to specify an EVENT IDENTIFIER clause. This may be a column of type CQL bigint and this column may have the same value for plus, minus, and update tuples for an event

In some cases, within the CQL Engine 156, the column specified in the EVENT IDENTIFIER clause may be utilized. For example, when the archiver is queried, this field is may be forced to be present in the SELECT list and use the values of this field to set the tupleId while converting the records into tuples. Also when a normal input event comes (e.g., when the query is running) the value in this field may be assigned as the tupleId while converting the TupleValue into ITuple in the Relation Source code. This may enable a configuration for ensuring that PLUS and MINUS of an event have the same tuple ID.

In some examples, the following syntax may be utilized for an archived relation DDL:

CREATE ARCHIVED RELATION SalesDataObjectChannel (region char(8), productid int, sales float, eventid bigint) ARCHIVER com.oracle.beam.PersistenceServiceArchiverImpl ENTITY “SALES_DO” EVENT IDENTIFIER eventid

This DDL to create the Archived Relation may be invisible to the end users and also also other components. For example, the creation of the archived relation may be handled “under the covers” by the CQL processor code when the EPN contains the Data Object node connected to a CQL processor node. For example, consider the following EPN: (SalesDataObjectNode for SALES_DO)→(SalesDataObjectChannel)→(CQL Processor)

This EPN code may use the field names of the Data Object as the column names of the archived relation that it creates in the CQL engine 156 thereby ensuring that the names of the fields and the order of the fields match.

Additionally, in some examples, archived streams may be enabled via the CQL engine 156 and/or other engines. Conceptually, an archived stream may be very similar to the Archived Relations feature. But owing to the semantic difference between a stream and a relation, certain changes may be made to the design and syntax of the archived stream as compared to the archived relation feature. For example, relation contents may undergo changes when additions, updates, or deletions occur. As such, the contents can grow or shrink in size with time. However, for a stream, by definition, updates and deletions are not possible. So the stream size may only keep increasing. Thus, the size of the past contents of a stream may be prohibitively large and most of the times a user would be interested in only a subset of the immediate past maintained by the archiver.

As such, the following syntax may be utilized for an archived stream DDL:

CREATE ARCHIVED STREAM <stream_name> ( stream schema ) ARCHIVER <archiver_name> ENTITY “<entity_name>” TIMESTAMP COLUMN <timestamp_col_name> REPLAY LAST ( <time_spec> | <intToken> ROWS) [IS SYSTEM TIMESTAMPED]

Here, the ARCHIVER and ENTITY clause may have the same meaning as with the archived relation 154. However, the EVENT IDENTIFIER clause may not needed since it is generally only for handling MINUS events which cannot come as input for a stream. Additionally, the REPLAY LAST clause may allow a user to specify the part of the immediate past that is of interest. The user can specify it either as a time range or in terms of number of rows. So, for example, the REPLAY clause can be REPLAY LAST 30 MINUTES (in which case the records that have arrived in the past 30 minutes may be fetched from the archiver) or REPLAY LAST 50 ROWS (in which case latest 50 records ordered by arrival time may be fetched from the archiver).

The TIMESTAMP COLUMN clause may be utilized for identification of records that may be returned while querying the archiver. This may be used in the WHERE clause of the archiver query that determines the records that are part of the result set of the archiver query. The values in this column may also be utilized while assigning the timestamp to the tuples (which may be obtained by querying the archiver) inside the CQL Engine 156. This column name could be the name of the column in the DO that has the creation timestamps assigned by BEAM persistence.

Additionally, in some examples, the configuration window module 150 may be configured to generate, receive, and/or determine a window size 158 for configuring one or more an archived relation 154 of the CQL engine 156. However, in some examples, defining different windows over an archived relation may not create separate archived relation instances. Instead, when a window is applied, there be only a single archived relation instance, and the window may determine the data in that archived relation which is of “interest” for that particular query. As noted above, the window size 158 may configure the size of the window w1, w2, and/or wN of the archived relation 154. In this way, the user may have control of the window size and may designate the size based at least in part on information associated with the business event data and/or personal concerns, business goals, and/or other factors, as desired.

Further, in some examples, the event counting module 152 may be configured to implement one or more listening services 160 within the CQL engine 156 or other engine configured to enable correct counting of change events within a stream or archived relation 154. As discussed briefly, when a continuous query 162 indicates a dependency on a stream and/or archived relation 164 managed by the CQL engine 156, the CQL engine 156 may implement the listening service 160. In at least some examples, the timing of the implementation of the listening service may determine whether or not change events in the stream/relation 164 are counted correctly. Additionally, as noted, in some examples, the continuous query 162 may be configured to initialize data of the archived relation 164 by querying against a data store 166 of historical and/or warehouse data.

In some examples, when a query is run in the CQL engine 156 it may initially run the query against the a DataObject backing store to establish the current state of the DataObject and then listen for and process change notifications from that DataObject. This creates two problems: change notifications may be missed while the CQL engine 156 is running the initial query; change notifications might be double-counted if the change is already in the initial query.

Missing change notifications can be eliminated by establishing the change notification listener before the initial query is started but not processing them until the archiver query execution is complete and/or the state initialization is done. These change notifications may be buffered in the messaging service (JMS) until the CQL engine 156 is ready to process them. In some cases, eliminating double-counting of change notifications may be performed by supplying additional information to a Persistence Service to allow the CQL engine 156 to determine which change notifications are included in the initial query result and which are not.

In some examples, an additional column may be added (e.g. DATAOBJECT_ID) to each DataObject that contains the transaction ID of the last transaction to affect that DataObject instance (row). However, in other examples, no additional column is added and, instead, a transaction context may be utilized. This transaction ID may be an internal BEAM artifact not to be confused with any other transaction mechanism such as JTA. This transaction ID may, in some examples, be a monotonically increasing integer. Some (or all) DataObject instances (e.g., rows) modified by the same JTA transaction may be tagged with the same transaction ID. Additionally, transaction IDs may be committed in ascending order. This same column may be included in DataObject change notifications. Given the above, if a query includes MAX(DATAOBJECT_TID), then the highest transaction ID present in our query result may be known. As such, the transaction ID value in any change notifications may be compared against the highest value because a value less than or equal may be ignored (i.e., because it may already be counted) and a value greater than may be processed (i.e., because it may not yet be counted).

However, in some cases, in order to have transaction IDs committed in ascending order, the DataObject transactions may be serialized. Yet, this may have a detrimental affect on concurrency. Still, concurrency may be increased by introducing the notation of a context ID. In some examples, each context ID may maintain its own transaction ID. Exclusive access to a BEAM context may then be acquired by JTA transactions that perform operations against BEAM DataObjects. This same BEAM context may then be used for operations (e.g., all operations) performed by that JTA transaction and ultimately released upon commit or rollback of the JTA transaction. This may allow processing to proceed in parallel across BEAM contexts. The level of concurrency may then be proportionate to the allocation of BEAM contexts. An additional column (DATAOBJECT_CID) can be added to each DataObject to hold the ID of the last context to modify that DataObject instance (row). However, in other examples, no additional column is added and, instead, a transaction context may be utilized. Context IDs, like transaction IDs, may also be included in DataObject change notifications. Yet, this may change the requirements on the query side in that one may need to obtain the MAX(DATAOBJECT_ID) for context IDs in order to eliminate double-counting.

In some examples, the same level of concurrency can be achieved without adding additional columns to the DataObject if the notion of a Transaction Context entity is introduced. A new Java class and associated JPA entity may then be created to maintain the state of context IDs in the database. The transaction context entity may contain a context ID and its associated (highest, last used) transaction ID. The context ID may be generated as a sequence and may be the primary key for the entity.

When a Persistence Service is initialized it may create a configured number of transaction context instances. These transaction context instances may be for the sole use of that Persistence Service. If another Persistence Service is initialized on another Server, it too may create a configured number of transaction context instances. In this fashion each Persistence Service may be guaranteed to have a unique set of contexts. The Persistence Service may create instances of transaction context and may persist them via JPA. Since this is a sequenced entity and the sequence is the context ID the transaction context instances created may be automatically unique. Each transaction context created may get the next sequence number. When a Persistence Service is shutdown it may delete the transaction context instances that it created. In some cases, this may remove them from the database.

In some examples, DataObject operations (e.g., all or some DataObject operations) may ultimately be made through an EJB method (e.g., called processDataObjectOperations). This method may take a collection of DataObjectOperations of which there is a derivation for insert, update, upsert, and/or delete. Each DataObjectOperations may specify a target DataObject by name, a particular operation, and the required data for that operation. The DataObjectOperations can contain any combination of DataObjectOperation targeting and/or any number of DataObjects. The DataObjectOperation may be executed in the order in which they were added to the DataObjectOperations. The processDataObjectOperations method may be defined as TransactionAttributeType.REQUIRED which means that if called within a JTA transaction, it may participate in that transaction. However, if called outside a JTA transaction, the application server may start a JTA transaction for the duration of the method call. In some instances, this means that processDataObjectOperations may always be operating within a JTA transaction. Additionally, all or some operations against a DataObject may occur within a JTA transaction.

In some examples, eliminating double counting of change events may be enabled by the following operations (which may be performed in any appropriate order, as desired. For example, when processDataObjectOperations are called (while the following operations are numbered, these numbers are merely to aid in explanation and shall not limit the set of operations to any particular order or to any operation being required):

-   -   1. An attempt may be made to fetch the transaction context from         the associated JTA transaction. If there is an associated         transaction context then it may be used. However, if there is no         transaction context associated then:         -   a) An exclusive lock may be obtained on a transaction             context instance from the set of available transaction             context instances (pool) created by the Persistence Service             on startup. If a transaction context is not available the             call may be blocked until a transaction context becomes             available. This locking may be done in Java and/or in the             database.         -   b) The transaction ID in this transaction context may be             incremented to the next number in sequence which may become             the transaction ID for the associated JTA transaction.         -   c) The transaction context instance may be “attached” to the             JTA transaction as an application resource. This may allow             the Persistence Service to obtain the transaction context             from its associated JTA transaction (e.g., as in operation             #1 above) should multiple calls be made within that one JTA             transaction. This may assure that the same transaction             context may be used for the operations performed within the             same JTA transaction regardless if that JTA transaction was             started from within or without the BEAM Server.         -   d) The transaction context instance may be added as a             transaction synchronization listener to the associated JTA             transaction. This may allow the Persistence Service to be             informed when the JTA transaction completes so it can take             appropriate action.         -   e) The transaction context entity with the incremented             transaction ID may be merged. In some examples, this             database update may also be happening within the associated             JTA transaction.     -   2. The specified DataObject operations may be performed. Change         notifications triggered may be tagged with the context ID and         transaction ID from the transaction context.     -   3. The processDataObjectOperations method call may complete.     -   4. Should additional calls be made within the same JTA         transaction, operation #1 above may pick up the “attached”         transaction context and proceed to operation #2.     -   5. In some cases, if the JTA transaction commits:         -   a) DataObject operations performed may be committed to the             database.         -   b) DataObject change notifications may be sent (JMS).         -   c) The transaction context merge may be committed.         -   d) Persistence may be notified that the transaction has             completed and may release the transaction context back to             the pool for use by a subsequent transaction. In some             aspects, this may occur at some point in time after the             commit.     -   6. In some cases, if the JTA transaction rolls back:         -   a) DataObject operations performed may be rolled back.         -   b) DataObject change notifications may be discarded (JMS).         -   c) The BeamTransactionContext merge may be rolled back.         -   d) Persistence may be notified that the transaction has             completed so it may release the transaction context back to             the pool for use by a subsequent transaction. In some             aspects, this may happen after roll back.

In some example, when executing a query to obtain the initial state from the DataObject backing store they query may be executed atomically to also include UNION in the transaction context table. In this fashion query results plus the highest committed transaction ID for each BEAM context for all the data in our query result may be received. The transaction context information allows any DataObject change notifications to be checked to eliminate double-counting by checking the IDs in the change notification against the IDs in the transaction context table. Alternatively, or in addition, snapshot information at the querying instant may also be derived from the transaction context table. This snapshot information may be maintained in the CQL Engine and a snapshotID (increasing identifier) may be associated with it. The same may be set in the input queues of some selected operators in that query's plan. These are called ‘connector’ operators and they may represent the place at which a local query plan may join the global (overall) query plan. When an event arrives in CQL Engine, a snapshotID may be computed for that event using the context ID and transaction ID values in it. The snapshotID may be computed using the snapshot information maintained in CQL Engine. The snapshotID of the event may then be compared with the snapshotID of the input queue. If the ID in the event>ID in the queue then it may be processed otherwise it may have already been accounted for before and may therefore ignored to avoid double-counting.

In some examples, the persistence layer may supply a context ID (worker identifier) and a transaction ID (transaction identifier) with each change event notification and/or the persistence layer may maintain the transaction context table. Additionally, at query start time, the CQL Engine may query the ‘snapshot’ information (worker identifier, transaction identifier pairs) from the transaction context table and associate an increasing snapshot ID with it. The CQL Engine may also set the snapshot ID at the input queue of the “connector” operator at start time. Additionally, at query run time, the CQL Engine may use the worker identifier and/or transaction identifier fields in the input event and the maintained “snapshot” information to compute a Snapshot Id for each input event. At query runtime, the CQL Engine may also compare the snapshot ID of the input event and the one set in the input queue (at query start) to decide whether to process or ignore an event. The following is an example of general form of a DDL for worker and transaction ID clauses:

CREATE ARCHIVED RELATION <relation_name> (schema) ARCHIVER <archiver_name> ENTITY “entity_name” EVENT IDENTIFIER <col_name> WORKER IDENTIFIER <col_name> TRANSACTION IDENTIFIER <col_name> IS SYSTEM TIMESTAMPED

In some examples, an Archiver may be maintained by the CQ Service; an Entity may be the name of the Data Object as a quoted string; the Event ID may be a column of type long which may act as a unique event ID column for this relation; the Worker ID may be a column of type long which may map to the context ID column in persistence generated change notification; and the Transaction ID may be a column of type long which may map to the transaction ID column in persistence generated change notification. The following is an example implementation:

CREATE ARCHIVED RELATION sales_info (prodid integer, sales double, eid bigint, wid bigint, tid bigint) ARCHIVER myArchiver ENTITY “sales_do” EVENT IDENTIFIER eid WORKER IDENTIFIER wid TRANSACTION IDENTIFIER tid IS SYSTEM TIMESTAMPED Similarly, in some examples, these two clauses may be added after a REPLAY clause for archived streams.

As previously mentioned, there may be no need to actually tag each DataObject instance with the last context and transaction ID that modified it. In some examples, this information can be received instead from the transaction context entity. One way to accomplish this, as stated previously, is to atomically query both the desired data from the DataObject(s) as well as the contents of the transaction context entity. For atomicity, this may be performed using only one query. For example, using the UNION clause which allows the result set from two disparate queries to be appended in a single query. In some examples, the DataObject(s) and/or the Persistence service described above may be embodied by the data store 166 of FIG. 1.

Additional types of computer storage media (which may also be non-transitory) that may be present in the service provider computers 106 and/or user devices 104 may include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the service provider computers 106 and/or user devices 104. Combinations of any of the above should also be included within the scope of computer-readable media.

Alternatively, computer-readable communication media may include computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, computer-readable storage media does not include computer-readable communication media.

FIG. 3 depicts a simplified high level diagram of an event processing system 300 that may incorporate an embodiment of the present disclosure a CQ Service 202 that is configured to provide an environment for processing event streams, and one or more event sinks (310, 312). The event sources generate event streams that are received by the CQ Service 202. The CQ Service 202 may receive one or more event streams from one or more event sources. For example, as shown in FIG. 3, the CQ Service 202 receives an input event stream 314 from event source 304, a second input event stream 316 from event source 306, and a third event stream 318 from event source 308. One or more event processing applications (320, 322, and 324) may be deployed on and be executed by the CQ Service 202. An event processing application executed by the CQ Service 202 may be configured to listen to one or more input event streams, process the events received via the one or more event streams based upon processing logic that selects one or more events from the input event streams as notable events. The notable events may then be sent to one or more event sinks (310, 312) in the form of one or more output event streams. For example, in FIG. 3, the CQ Service 202 outputs an output event stream 326 to event sink 310, and a second output event stream 328 to event sink 312. In certain embodiments, event sources, event processing applications, and event sinks are decoupled from each other such that one can add or remove any of these components without causing changes to the other components.

In one embodiment, the CQ Service 202 may be implemented as a Java server comprising a lightweight Java application container, such as one based upon Equinox OSGi, with shared services. In some embodiments, the CQ Service 202 may support ultra-high throughput and microsecond latency for processing events, for example, by using JRockit Real Time. The CQ Service 202 may also provide a development platform (e.g., a complete real time end-to-end Java Event-Driven Architecture (EDA) development platform) including tools (e.g., Oracle CEP Visualizer and Oracle CEP IDE) for developing event processing applications.

An event processing application is configured to listen to one or more input event streams, execute logic (e.g., a query) for selecting one or more notable events from the one or more input event streams, and output the selected notable events to one or more event sources via one or more output event streams. FIG. 3 provides a drilldown for one such event processing application 320. As shown in FIG. 3, event processing application 320 is configured to listen to input event stream 318, execute a query 330 comprising logic for selecting one or more notable events from input event stream 318, and output the selected notable events via output event stream 328 to event sink 312. Examples of event sources include, without limitation, an adapter (e.g., JMS, HTTP, and file), a channel, a processor, a table, a cache, and the like. Examples of event sinks include, without limitation, an adapter (e.g., JMS, HTTP, and file), a channel, a processor, a cache, and the like.

Although event processing application 320 in FIG. 3 is shown as listening to one input stream and outputting selected events via one output stream, this is not intended to be limiting. In alternative embodiments, an event processing application may be configured to listen to multiple input streams received from one or more event sources, select events from the monitored streams, and output the selected events via one or more output event streams to one or more event sinks. The same query can be associated with more than one event sink and with different types of event sinks.

Due to its unbounded nature, the amount of data that is received via an event stream is generally very large. Consequently, it is generally impractical and undesirable to store or archive all the data for querying purposes. The processing of event streams requires processing of the events in real time as the events are received by the CQ Service 202 without having to store all the received events data. Accordingly, the CQ Service 202 provides a special querying mechanism that enables processing of events to be performed as the events are received by the CQ Service 202 without having to store all the received events.

Event-driven applications are rule-driven and these rules may be expressed in the form of continuous queries that are used to process input streams. A continuous query may comprise instructions (e.g., business logic) that identify the processing to be performed for received events including what events are to be selected as notable events and output as results of the query processing. Continuous queries may be persisted to a data store and used for processing input streams of events and generating output streams of events. Continuous queries typically perform filtering and aggregation functions to discover and extract notable events from the input event streams. As a result, the number of outbound events in an output event stream is generally much lower than the number of events in the input event stream from which the events are selected.

Unlike a SQL query that is run once on a finite data set, a continuous query that has been registered by an application with the CQ Service 202 for a particular event stream may be executed each time that an event is received in that event stream. As part of the continuous query execution, the CQ Service 202 evaluates the received event based upon instructions specified by the continuous query to determine whether one or more events are to be selected as notable events, and output as a result of the continuous query execution.

Unlike a SQL query that is run once on a finite data set, a continuous query that has been registered by an application with EPS 302 for a particular event stream may be executed each time that an event is received in that event stream. As part of the continuous query execution, EPS 302 evaluates the received event based upon instructions specified by the continuous query to determine whether one or more events are to be selected as notable events, and output as a result of the continuous query execution.

The continuous query may be programmed using different languages. In certain embodiments, continuous queries may be configured using the CQL provided by Oracle Corporation and used by Oracle's Complex Events Processing (CEP) product offerings. Oracle's CQL is a declarative language that can be used to program queries (referred to as CQL queries) that can be executed against event streams. In certain embodiments, CQL is based upon SQL with added constructs that support processing of streaming events data.

In one embodiment, an event processing application may be composed of the following component types:

(1) One or more adapters that interface directly to the input and output stream and relation sources and sinks. Adapters are configured to understand the input and output stream protocol, and are responsible for converting the event data into a normalized form that can be queried by an application processor. Adapters may forward the normalized event data into channels or output streams and relation sinks. Event adapters may be defined for a variety of data sources and sinks. (2) One or more channels that act as event processing endpoints. Among other things, channels are responsible for queuing event data until the event processing agent can act upon it. (3) One or more application processors (or event processing agents) are configured to consume normalized event data from a channel, process it using queries to select notable events, and forward (or copy) the selected notable events to an output channel. (4) One or more beans are configured to listen to the output channel, and are triggered by the insertion of a new event into the output channel. In some embodiments, this user code is a plain-old-Java-object (POJO). The user application can make use of a set of external services, such as JMS, Web services, and file writers, to forward the generated events to external event sinks. (5) Event beans may be registered to listen to the output channel, and are triggered by the insertion of a new event into the output channel. In some embodiments, this user code may use the Oracle CEP event bean API so that the bean can be managed by Oracle CEP.

In one embodiment, an event adapter provides event data to an input channel. The input channel is connected to a CQL processor associated with one or more CQL queries that operate on the events offered by the input channel. The CQL processor is connected to an output channel to which query results are written.

In some embodiments, an assembly file may be provided for an event processing application describing the various components of the event processing application, how the components are connected together, event types processed by the application. Separate files may be provided for specifying the continuous query or business logic for selection of events.

It should be appreciated that system 300 depicted in FIG. 3 may have other components than those depicted in FIG. 3. Further, the embodiment shown in FIG. 3 is only one example of a system that may incorporate an embodiment of the present disclosure. In some other embodiments, system 300 may have more or fewer components than shown in FIG. 3, may combine two or more components, or may have a different configuration or arrangement of components. System 300 can be of various types including a personal computer, a portable device (e.g., a mobile telephone or device), a workstation, a network computer, a mainframe, a kiosk, a server, or any other data processing system. In some other embodiments, system 300 may be configured as a distributed system where one or more components of system 300 are distributed across one or more networks in the cloud.

The one or more of the components depicted in FIG. 3 may be implemented in software, in hardware, or combinations thereof. In some embodiments, the software may be stored in memory (e.g., a non-transitory computer-readable medium), on a memory device, or some other physical memory and may be executed by one or more processing units (e.g., one or more processors, one or more processor cores, one or more GPUs, etc.).

FIG. 4 illustrates a simplified block diagram 400 with which features of the management of archived relations may be described. As shown in FIG. 4, an archived relation may be represented as a query graph 402. In some examples, a query graph 402 may include nodes that represent operators of the query and vertices that represent a path between the operators of the query graph 402. In one non-limiting example, the query graph 402 of FIG. 4 includes a Project operator 404, a Group By operator 406, and a Relational Source operator 408. Further, in some examples, the Project operator 404 and the Relational Source 408 may be stateless, while the Group By operator 406 may be stateful. In some cases, stateless operators do not keep track of, manage, or otherwise request state, while stateful operators do. As noted above, in some instances, the query graph 402 may be analyzed or otherwise evaluated 410 in a top down fashion, importing historical data at stateful operators (in some examples, at the first or lowest stateful operator). While analyzing 410 the query graph 402, a service and/or engine (e.g., the CQ Service 202 and/or CQL engine 156 as described with reference to FIGS. 1-3) may be configured to determine the first stateful operator in the query graph 402. In the example of FIG. 4, the first stateful operator is Group By 406. As such, when the service reaches the Project operator 404 (which is stateless in this example), table data (i.e., historical data) may not be imported at 412. However, at 414, when the Group By operator 406 is reached, the historical, warehouse, and/or table data may be imported to initialize the archived relation.

Alternatively, or in addition, in some examples, the query graph 402 (also referred to as a plan) may be traversed in topological order starting from the source (here, the Relational Source operator 408). As such, in this example, the traversal may be in a bottom up fashion. In this traversing when the first stateful operator is reached, it may be marked as query operator and then the graph 402 may not need to be traversed further in that branch. Note that for some CQL queries like aggregate distinct, the query plan may have more than one branch. In the current example, Relational Source 408 may be stateless so the traversal may move up and see Group By 406. Since Group By 406 may be stateful it may be marked as the query operator. As such, the traversal may be complete, and may not need to go up to the Project operator 404 since Group By 406 would query the archiver, populate its state, and also propagate the snapshot output to Project 404, and further to downstream operators if any.

FIG. 5 illustrates at least one non-limiting example 500 for counting change events associated with archived relations utilizing one or more table IDs such as, but not limited to, a TRANSACTION_CID and/or a TRANSACTION_TID (as described above). As show in FIG. 5, an initial Transaction Context Table 502 and a Transaction Context Table after Insert 504 are shown. In some examples, a server configured to manage the transaction IDs may be initialized or otherwise started. When a Persistence Service is started by this server it may create a set of Transaction instances. As such, the Transaction Context Table 502 illustrates the contents of the after a single Persistence Service is started which created 10 context instances for its own use. The TRANSACTION_CID column contains the context ID and the TRANSACTION_TID column contains the highest transaction ID committed by that context ID.

In one non-limiting example, if a second Persistence Service started at this point, that also created 10 context instances for its own use, the Table 502 may illustrate 10 new entries with TRANSACTION_CID values of 11-20. Now that the Persistence Service is running a DataObject named “Alpha” containing one of each of the DataObject column data types may be created. In some examples, whenever a DataObject is created the Persistence Service may create a corresponding database View representing the persistent store for that DataObject. In one example, once the DataObject is generated, insert commands may be performed against it. In order to best illustrate the processing of context and transaction IDs, two insert operations per thread using 12 threads for a total of 24 inserts may be performed. Each thread may start a JTA transaction, perform one insert operation, perform a second insert operation and then commit the transaction. The reason for using multiple threads is that it may create multiple JTA transactions executing in parallel which will better illustrate how the context ID comes into play. This also demonstrates the scenario where multiple (two per thread in this example) DataObject operation method calls are made within the same JTA transaction and where that JTA transaction was started and committed outside of Persistence.

For this example, 12 threads may be running the code simultaneously. Each thread may start a transaction outside of the server, make two insert calls to Persistence and then commit the transaction. Since Persistence has allocated 10 context IDs, 10 of these threads may obtain a context while 2 may initially be blocked. Two JTA transactions may be blocked until another JTA transaction completes and releases the context. The blocked JTA transaction may then grab the released context and process the Persistence API call. In some examples, after the insert operations are completed an examination of the Table 504 (after insert) shows this very result. Transaction contexts 1 and 2 show transaction ID 2 as the “last committed” transaction IDs while all other transaction contexts show transaction ID 1 as their last committed transaction.

In some examples, DataObject change notifications may be broadcast via JMS as a result of the insert operations performed in this example. Remember, two inserts were performed per JTA transaction and 12 transactions were executed for a total of 24 insert operations. Transaction contexts 1 and 2 were used for two transactions each so we should see 4 change notifications from contexts 1 and 2 having transaction ID 1 for two inserts and transaction ID 2 for the other two inserts. All other contexts were used for only one transaction and should have generated two inserts both with transaction ID 1.

FIGS. 6-8 illustrate example flow diagrams showing respective processes 600, 700, and 800 for implementing the management of continuous queries with archived relations described herein. These processes 600, 700, and 800 are illustrated as logical flow diagrams, each operation of which represents a sequence of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

Additionally, some, any, or all of the processes may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.

In some examples, the one or more service provider computers 106 (e.g., utilizing at least the archived relation module 148) shown in at least FIG. 1 (and others) may perform the process 600 of FIG. 6. The process 600 may begin at 602 by including identifying and/or receiving a query that identifies a archived stream or archived relation as a data source. In some examples, at 604, the process 600 may include initializing the query with historical data. At 606, the process 600 may include evaluating the query based at least in part on the archived stream or archived relation and the historical data. At 608, the process 600 may also include forming a query graph representing operators of the query. The process 600 may include traversing the query graph from the top of the graph down at 610. Further, in some examples, the process 600 may end at 612 by including initializing the query with the historical data at a first stateful operator identified in the query graph.

FIG. 7 illustrates an example flow diagram showing process 700 for implementing the management of continuous queries with archived relations described herein. The one or more service provider computers 106 (e.g., utilizing at least the archived relation module 148) shown in at least FIG. 1 may perform the process 700 of FIG. 7. The process 700 may begin at 702 by including receiving a continuous query to process a data stream or an archived relation including an ID for a data stream or historical data. At 704, the process 700 may include generating a query graph based at least in part on the received continuous query. Additionally, in some examples, the process 700 may include initializing the continuous query with a portion of the historical data. Further, the process 700 may end, at 708, by including evaluating the continuous query with respect to the data stream or the archived relation and based at least in part on the historical data.

FIG. 8 illustrates an example flow diagram showing process 800 for implementing the management of continuous queries with archived relations described herein. The one or more service provider computers 106 (e.g., utilizing at least the archived relation module 148) shown in at least FIG. 1 may perform the process 800 of FIG. 8. The process 800 may begin at 802 by including receiving a continuous query to process a stream or archived relation associated with business event data. At 804, the process 800 may include generating a query graph based at least in part on the continuous query. At 806, the process 800 may include traversing the query graph topologically from the source to identify a lowest stateful operator (e.g., the lowest stateful operator may be the last stateful operator identified while traversing and/or it may be an operator of a branch). In some examples, at 808, the process 800 may include determining an optimal amount of historical data for initializing based at least in part on the operator of the query. At 810, the process 800 may include initializing the continuous query with historical data at an identified lowest stateful operator. Further, in some examples, the process 800 may end by including evaluating the continuous query with respect to the data stream or the archived relation based at least in part on historical data at 812.

FIGS. 9-11 illustrate example flow diagrams showing respective processes 900, 1000, and 1100 for implementing the archived relations with configurable data windows described herein. These processes 900, 1000, 1100 are illustrated as logical flow diagrams, each operation of which represents a sequence of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

Additionally, some, any, or all of the processes may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.

In some examples, the one or more service provider computers 106 (e.g., utilizing at least the configurable window module 150) shown in at least FIG. 1 may perform the process 900 of FIG. 9. The process 900 may begin at 902 by including identifying or otherwise receiving a query that identifies a data stream or archived relation. At 904, the process 900 may include identifying a user-configured window size. At 906, the process 900 may include initializing the query with historical data based at least in part on the window size. Further, the process 900 may end at 908 by including evaluating the query based at least in part on the historical data as well as the archived stream or archived relation.

FIG. 10 illustrates an example flow diagram showing process 1000 for implementing the archived relations with configurable data windows described herein. The one or more service provider computers 106 (e.g., utilizing at least the configurable window module 150) shown in at least FIG. 1 may perform the process 1000 of FIG. 10. The process 1000 may begin at 1002 by including receiving a continuous query configured to process a data stream or an archived relation. At 1004, the process 1000 may include generating a query graph based at least in part on the continuous query. At 1006, the process 1000 may include computing the window size from the continuous query configured to process a data stream or an archived relation. In some examples, at 1008, the process 1000 may include determining an amount of historical data for initialization based at least in part on the window size. At 1010, the process 1000 may include initializing the continuous query with the determined historical data. Further, at 1012, the process 1000 may include evaluating the continuous query with respect to the archived stream or archived relation, and the window size.

FIG. 11 illustrates an example flow diagram showing process 1100 for implementing the archived relations with configurable data windows described herein. The one or more service provider computers 106 (e.g., utilizing at least the configurable window module 150) shown in at least FIG. 1 may perform the process 1100 of FIG. 11. The process 1100 may begin at 1102 by including receiving a continuous query configured to process a archived stream or archived relation. At 1104, may include computing the window size from continuous query to identify a bounded range of stream or archived relation to process. At 1106, the process 1100 may include generating a query graph based at least in part on the continuous query. Additionally, in some aspects, the process 1100 may include traversing the query graph downward (e.g., top down approach) in order to identify a stateful operator. At 1110, the process 1100 may include determining an optimal amount of historical data for initializing. At 1112, the process 1100 may include initializing the continuous query with historical data at an identified stateful operator. Further, in some examples, the process 1100 may include evaluating the continuous query with respect to the stream or archived relation, and based at least in part on the window size.

FIGS. 12-14 illustrate example flow diagrams showing respective processes 1200, 1300, and 1400 for implementing the event counting features associated with archived relations described herein. These processes 1200, 1300, 1400 are illustrated as logical flow diagrams, each operation of which represents a sequence of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

Additionally, some, any, or all of the processes may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.

In some examples, the one or more service provider computers 106 (e.g., utilizing at least the event counting module 152) shown in at least FIG. 1 may perform the process 1200 of FIG. 12. The process 1200 may begin at 1202 by including identifying a query that identifies a data object. At 1204, the process 1200 may include evaluating a query against historical data associated with the data object. At 1206, the process 1200 may include registering a listening service with the data object. The process 1200 may also include receiving a transaction ID for change identified by the listening service at 1208. In some examples, at 1210, the process 1200 may include comparing the transaction ID with a highest transaction ID of historical data. At 1212, the process 1200 may include processing the change only when the received transaction ID is greater than the highest transaction ID. At 1214, the process 1200 may end by including evaluating query based at least in part on the data object and historical data.

FIG. 13 illustrates an example flow diagram showing process 1300 for implementing the archived relations with configurable data windows described herein. The one or more service provider computers 106 (e.g., utilizing at least the event counting module 152) shown in at least FIG. 1 may perform the process 1300 of FIG. 13. The process 1300 may begin at 1302 by including receiving a continuous query that identifies or otherwise receives a data object. At 1304, the process 1300 may include registering a listening service associated with the data object. Additionally, in some examples, the process 1300 may include evaluating a continuous query against historical data after registration of the listening service at 1306. At 1308, the process 1300 may include processing changes identified by the listening service after evaluation against the historical data. At 1310, the process 1300 may end by including evaluating the continuous query against the data object.

FIG. 14 illustrates an example flow diagram showing process 1400 for implementing the archived relations with configurable data windows described herein. The one or more service provider computers 106 (e.g., utilizing at least the event counting module 152) shown in at least FIG. 1 may perform the process 1400 of FIG. 14. The process 1400 may begin at 1402 by including receiving a continuous query configured to process a data object. At 1404, the process 1400 may include registering a listening service with the data object. At 1406, the process 1400 may include evaluating the continuous query against historical data associated with the data object. In some examples, the process 1400 may also include receiving a transaction ID for changes identified by the listening service at 1408. Additionally, at 1410, the process 1400 may include comparing the received transaction ID with the highest transaction ID currently associated with the historical data. At 1412, the process 1400 may include processing changes when the received ID is greater than the highest ID associated with historical data. At 1414, the process 1400 may end by including evaluating the continuous query with respect to the data object.

Illustrative methods and systems for implementing the hybrid execution of continuous and scheduled queries are described above. Some or all of these systems and methods may, but need not, be implemented at least partially by architectures and processes such as those shown at least in FIGS. 1-14 above.

FIG. 15 is a simplified block diagram illustrating components of a system environment 1500 that may be used in accordance with an embodiment of the present disclosure. As shown, system environment 1500 includes one or more client computing devices 1502, 1504, 1506, 1508, which are configured to operate a client application such as a web browser, proprietary client (e.g., Oracle Forms), or the like over one or more networks 1510 (such as, but not limited to, networks similar to the networks 108 of FIGS. 1 and 3). In various embodiments, client computing devices 1502, 1504, 1506, and 1508 may interact with a server 1512 over the networks 1510.

Client computing devices 1502, 1504, 1506, 1508 may be general purpose personal computers (including, by way of example, personal computers and/or laptop computers running various versions of Microsoft Windows and/or Apple Macintosh operating systems), cell phones or PDAs (running software such as Microsoft Windows Mobile and being Internet, e-mail, SMS, Blackberry, or other communication protocol enabled), and/or workstation computers running any of a variety of commercially-available UNIX or UNIX-like operating systems (including without limitation the variety of GNU/Linux operating systems). Alternatively, client computing devices 1502, 1504, 1506, and 1508 may be any other electronic device, such as a thin-client computer, Internet-enabled gaming system, and/or personal messaging device, capable of communicating over a network (e.g., network 1510 described below). Although exemplary system environment 1500 is shown with four client computing devices, any number of client computing devices may be supported. Other devices such as devices with sensors, etc. may interact with server 1512.

System environment 1500 may include networks 1510. Networks 1510 may be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, network 1510 can be a local area network (LAN), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (VPN); the Internet; an intranet; an extranet; a public switched telephone network (PSTN); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth protocol known in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks.

System environment 1500 also includes one or more server computers 1512 which may be general purpose computers, specialized server computers (including, by way of example, PC servers, UNIX servers, mid-range servers, mainframe computers, rack-mounted servers, etc.), server farms, server clusters, or any other appropriate arrangement and/or combination. In various embodiments, server 1512 may be adapted to run one or more services or software applications described in the foregoing disclosure. For example, server 1512 may correspond to a server for performing processing described above according to an embodiment of the present disclosure.

Server 1512 may run an operating system including any of those discussed above, as well as any commercially available server operating system. Server 1512 may also run any of a variety of additional server applications and/or mid-tier applications, including HTTP servers, FTP servers, CGI servers, Java servers, database servers, and the like. Exemplary database servers include without limitation those commercially available from Oracle, Microsoft, Sybase, IBM and the like.

System environment 1500 may also include one or more databases 1514, 1516. Databases 1514, 1516 may reside in a variety of locations. By way of example, one or more of databases 1514, 1516 may reside on a non-transitory storage medium local to (and/or resident in) server 1512. Alternatively, databases 1514, 1516 may be remote from server 1512, and in communication with server 1512 via a network-based or dedicated connection. In one set of embodiments, databases 1514, 1516 may reside in a storage-area network (SAN) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to server 1512 may be stored locally on server 1512 and/or remotely, as appropriate. In one set of embodiments, databases 1514, 1516 may include relational databases, such as databases provided by Oracle, that are adapted to store, update, and retrieve data in response to SQL-formatted commands.

FIG. 16 is a simplified block diagram of a computer system 1600 that may be used in accordance with embodiments of the present disclosure. For example service provider computers 106 may be implemented using a system such as system 1600. Computer system 1600 is shown comprising hardware elements that may be electrically and/or communicatively coupled via a bus 1601. The hardware elements may include one or more central processing units (CPUs) 1602, one or more input devices 1604 (e.g., a mouse, a keyboard, etc.), and one or more output devices 1606 (e.g., a display device, a printer, etc.). Computer system 1600 may also include one or more storage devices 1608. By way of example, the storage device(s) 1608 may include devices such as disk drives, optical storage devices, and solid-state storage devices such as a random access memory (RAM) and/or a read-only memory (ROM), which can be programmable, flash-updateable and/or the like.

Computer system 1600 may additionally include a computer-readable storage media reader 1612, a communications subsystem 1614 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.), and working memory 1618, which may include RAM and ROM devices as described above. In some embodiments, computer system 1600 may also include a processing acceleration unit 1616, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.

Computer-readable storage media reader 1612 can further be connected to a computer-readable storage medium 1610, together (and, optionally, in combination with storage device(s) 1608) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information. Communications system 1614 may permit data to be exchanged with network 1612 and/or any other computer described above with respect to system environment 1600.

Computer system 1600 may also comprise software elements, shown as being currently located within working memory 1618, including an operating system 1620 and/or other code 1622, such as an application program (which may be a client application, Web browser, mid-tier application, RDBMS, etc.). In an exemplary embodiment, working memory 1618 may include executable code and associated data structures used for relying party and open authorization-related processing as described above. It should be appreciated that alternative embodiments of computer system 1600 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.

FIG. 17 illustrates another example flow diagram showing process 1700 for implementing the management of continuous queries with archived relations described herein. The one or more service provider computers 106 (e.g., utilizing at least the archived relation module 148) shown in at least FIG. 1 may perform the process 1700 of FIG. 17. The process 1700 may begin at 1702 by including identifying a query as being based at least in part on an archived relation. At 1704, the process 1700 may include generating a query operator graph utilizing operators of the query. Additionally, in some examples, the process 1700 may include sorting the operator graph (e.g., topologically) at 1706. At 1708, the process 1700 may include analyzing the graph to determine operator(s) that may query the archiver to initialize the state (e.g., stateful operators). At 1710, the process 1700 may include constructing an appropriate query (e.g., an archiver query) to be given the archiver. In some examples, the process 1700 may also include deciding on operator sharing at 1712. At 1714, the process 1700 may include initializing the state of the determined operator(s) by issuing the archiver query to the CQ Service (e.g., as described above). At 1716, the process 1700 may receive historical results (e.g., from the CQ Service or persistence). Further, the process 1700 may end, at 1718, by including processing incoming events, if not already counted, as part of querying the historical results.

FIG. 18 illustrates another example flow diagram showing process 1800 for implementing the management of continuous queries with archived relations described herein. The one or more service provider computers 106 (e.g., utilizing at least the configurable window module 150) shown in at least FIG. 1 may perform the process 1800 of FIG. 18. The process 1800 may begin at 1802 by including evaluating an archiver query on an archiver source and obtaining one or more snapshot outputs. At 1804, the process 1800 may include specifying a window on a relation utilizing at least one of two configurable parameters. The configurable parameters include window size and/or relation attribute). Additionally, in some examples, the process 1800 may include testing, for each snapshot tuple, whether the tuple lies within a window by comparing a designated attribute's value with a current event time at 1806. At 1808, the process 1800 may include determining whether the snapshot tuple passed the test. In some examples, if the test is passed, at 1810, the process 1800 may include inserting the tuple in the window. However, in some examples, if the test is not passed, the process 1800 may instead include ignoring the tuple at 1812. The process 1800 may then return to 1802 to end or to include evaluating the next archiver query.

FIG. 19 illustrates another example flow diagram showing process 1900 for implementing the management of continuous queries with archived relations described herein. The one or more service provider computers 106 (e.g., utilizing at least the event counting module 152) shown in at least FIG. 1 may perform the process 1900 of FIG. 19. The process 1900 may begin at 1902 by including querying a data object for a state operator. At 1904, the process 1900 may include deriving snapshot information from a transaction context table. At 1906, the process 1900 may include maintaining the snapshot information in a CQL Engine and increasing an associated snapshot ID. At 1908, the process 1900 may include setting a snapshot ID in a “connector” operator of the query plan. The “connector” operator may join local plans with global plans. At 1910, the process 1900 may include computing a snapshot ID for arriving events using the context ID (CID) and the transaction ID (TID) in the event. At 1912, the process 1900 may include comparing the snapshot ID of the event with the snapshot ID of an input queue. At 1914, the process 1900 may include determining whether the ID in the event is greater than the ID of the input queue. In some examples, if the event ID is greater than the queue ID, at 1914, the process 1900 may include processing the event. However, in some examples, if the event ID is not greater than the queue ID at 1914, the process 1900 may instead include ignoring the event at 1918. The process 1900 may then return to 1902 to end or to begin again.

Storage media and computer readable media for containing code, or portions of code, can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to, volatile and non-volatile (non-transitory), removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, data signals, data transmissions, or any other medium which can be used to store or transmit the desired information and which can be accessed by a computer.

Although specific embodiments of the disclosure have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the disclosure. Embodiments of the present disclosure are not restricted to operation within certain specific data processing environments, but are free to operate within a plurality of data processing environments. Additionally, although embodiments of the present disclosure have been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of the present disclosure is not limited to the described series of transactions and steps.

Further, while embodiments of the present disclosure have been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present disclosure. Embodiments of the present disclosure may be implemented only in hardware, or only in software, or using combinations thereof.

The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope. Illustrative methods and systems for providing features of the present disclosure are described above. Some or all of these systems and methods may, but need not, be implemented at least partially by architectures such as those shown in FIGS. 1-12 above.

Although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments could include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment. 

What is claimed is:
 1. A system, comprising: a memory storing a plurality of instructions; and one or more processors that access the memory, wherein the one or more processors execute the plurality of instructions to at least: identify a continuous query that identifies a data stream; identify a configurable window size; generate a data object to include at least a portion of historical data and that is configured to receive incoming events of the identified data stream that are within a window that corresponds to the configurable window size, the historical data associated with the identified data stream; initialize the continuous query with the data object to process at least the portion of the historical data based at least in part on the window size; and evaluate the data object using the continuous query based at least in part on the data stream and the portion of the historical data.
 2. The system of claim 1, wherein the continuous query processes incoming real-time business event data of the data stream.
 3. The system of claim 1, wherein the evaluation of the data object includes at least applying the continuous query against the data stream based at least in part on the configurable window size.
 4. The system of claim 1, wherein the data stream comprises a relation configured with a second configurable window size for referencing a portion of the data stream within a second window with a size based at least in part on a second configurable window size.
 5. The system of claim 4, wherein the second window moves along the data stream with time.
 6. The system of claim 1, wherein the historical data is not included in the data stream at a time after initializing the query.
 7. The system of claim 1, wherein the historical data comprises business event data from the data stream at a time before initializing the query.
 8. The system of claim 1, wherein evaluating the data object includes at least forming a query graph with nodes representing operators of the continuous query.
 9. The system of claim 8, wherein at least one of the nodes identifies the window size.
 10. The system of claim 8, wherein the one or more processors are further configured to execute the plurality of instructions to at least traverse the query graph topographically from a source.
 11. The system of claim 10, wherein the one or more processors further execute the plurality of instructions to at least initialize the continuous query with at least the historical data at a lowest stateful operator identified in the query graph.
 12. A computer-readable memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising: instructions that cause the one or more processors to receive a continuous query configured to process data objects, the continuous query including at least one of an identifier of the data stream or an identifier of historical data; instructions that cause the one or more processors to generate a query graph based at least in part on the continuous query; instructions that cause the one or more processors to receive a window size from an entity associated with the data stream; instructions that cause the one or more processors to generate a data object to include at least a portion of the historical data and that is configured to receive incoming events of the data steam that are within a window that corresponds to the window size; instructions that cause the one or more processors to initialize the continuous query with the data object to process at least the portion of the historical data based at least in part on the window size; and instructions that cause the one or more processors to evaluate the data object using the continuous query based at least in part on the historical data.
 13. The computer-readable memory of claim 12, wherein the data object is identified by a data definition language annotation of the continuous query that identifies at least one of a location of the historical data, a source of the data object, operation information associated with processing the continuous query, one or more relevant columns of a database corresponding to the historical data, or a location for providing the output of the continuous query.
 14. The computer-readable memory of claim 12, wherein the plurality of instructions further comprise instructions that cause the one or more processors to determine an amount of historical data with which to initialize the continuous query based at least in part on the window size.
 15. The computer-readable memory of claim 12, wherein the continuous query is initialized with the at least a portion of the historical data at a stateful operator of the query graph while traversing the query graph topographically from a source of the query graph.
 16. A computer-implemented method, comprising: receiving a continuous query configured to process data objects associated with business event data, the continuous query including an identifier of historical data associated with the stream; generating a data object to include at least a portion of the historical data and that is configured to receive incoming events of the steam that are within a window that corresponds to the window size; receiving a window size configured to identify a bounded range of the data object to process; initializing the continuous query with the data object to process at least the portion of the historical data at the identified stateful operator based at least in part on the window size; and evaluating the data object using the continuous query based at least in part on the window size.
 17. The computer-implemented method of 16, wherein the historical data includes business event data from a point in time of the data object prior to initializing the continuous query.
 18. The computer-implemented method of 16, further comprising determining an optimal amount of the historical data with which to initialize the continuous query based at least in part on the operator of the continuous query.
 19. The computer-implemented method of claim 16, further comprising determining an optimal amount of the historical data with which to initialize the continuous query based at least in part on the window size.
 20. The computer-implemented method of claim 16, further comprising: generating a query graph based at least in part on the continuous query, the query graph including at least a node representing an operator of the continuous query; and traversing the query graph topographically from a source node of the query graph to identify a stateful operator. 